Internet Surfer 2.0

home *** CD-ROM | disk | FTP | other *** search

/ Internet Surfer 2.0 / Internet Surfer 2.0 (Wayzata Technology) (1996).iso / pc / text / mac / faqs.052 < prev next >

Wrap

Text File | 1996-02-12 | 27.8 KB | 659 lines

Frequently Asked Questions (FAQS);faqs.052 PHCO_1502 - fix for grep -f/-x. PHNE_1525 - gated EGP update packet fix. PHSS_1589 - glance/MI patch, conflict with Oracle. PHSS_1590 - same? PHCO_1611 - fbackup/frecover patch, supersedes PHCO_1131. PHKL_1602 - NFS mega-patch. Supersedes: PHKL_0736,PHKL_0836,PHKL_0876,PHKL_0942,PHKL_1102. PHCO_1624 - curses 8-bit character fix. PHSS_1628 - xterm inverse video problem. Supersedes PHSS_0784. PHSS_1634 - TVRX fix for SDRC. PHKL_1637 - NFS memory leak patch for 8.05. PHSS_1638 - Motif 1.2 internationalization locale problem. PHKL_1649 - absolute cursor position on ITE fix. PHSS_1651 - more scope ux patches. PHNE_1654 - X.400 megapatch. PHSS_1657 - Xt problems. Replaces PHSS_1510, requires PHSS_0956. PHSS_1660 - hpterm periodic patch. Replaces PHSS_1186, PHSS_0529. PHCO_1666 - ksh loop when SIGHUP trapped and window closed. PHSS_1679 - xterm periodic patch. Replaces PHSS_1628, PHSS_0784. PHNE_1682 - X.400 fixes. PHKL_1696 - Diskless cluster panic "Premature end of packet" PHNE_1710 - x.29 fixes. PHSS_1727 - phigs/PVRX fix. 9.0/9.01 patches ---------------- PHCO_1539 - Bourne shell problem with Kanji. PHSS_1627 - C compiler fixes (includes fixes to optimizer). PHSS_1644 - NLIO fixes. PHCO_1689 - getpwnam problem with NIS-exluded names. PHSS_1699 - Timber graphics core dump. PHKL_1745 - diskless STREAMS support. In order to get HP-UX OS patches, you must be on HP software support. You can get them by calling the Response Center, or by using the "hpsl" tool on support.mayfield.hp.com. It will allow you to FTP patches. As of 10/6/92, the following patches are available on 192.6.148.19 or support.mayfield.hp.com: PHCO_0505 PHCO_0538 PHSS_0560 PHNE_0734 PHKL_0743 PHSS_0779 PHSS_0780 PHSS_0784 PHSS_0788 PHNE_0818 PHNE_0899 PHKL_0901 PHKL_0902 PHNE_0936 PHNE_0985 PHNE_1009 PHNE_1010 PHKL_1011 PHKL_1065 PHNE_1070 PHKL_1102 PHCO_1131 PHSS_1183 PHKL_1193 PHSS_1305 PHNE_1330 PHNE_1360 PHCO_1423 An HP-UX patch mailing list exists. Information is traded between the members about patches of interest. Note that patches themselves are not to be e-mailed, and there is no FTP archive of patches. To join the mailing list, send mail to: hpux-patch-request@cv.ruu.nl including your email address. Not all mailers generate proper return addresses. [ Thanks to Bart Muyzer (bartm@cv.ruu.nl) for running the mailing list ] -------------------------------------------------------------------------------- 12) How can I send mail to an "hpdesk" address? For a person whose DESK address is: JANE DOE /HP1234/XY Ignore the subentity (XY) and use the form: jane_doe@hp1234.desk.hp.com Send them a test message and tell them to make a note of the return address, as forming internet addresses on DESK is a little more complicated. If there is an X.400 system between you and the DESK person, what you get back may look like a very strange internet address, but it generally works. [ Thanks to Bob Niland (rjn@hpfcso.FC.HP.COM) for this information. ] -------------------------------------------------------------------------------- 13) What are the known issues with porting BSD-based programs to HP-UX? Mike Peterson (system@alchemy.chem.utoronto.ca) periodically posts his list of BSD-HP tricks to comp.sys.hp. -------------------------------------------------------------------------------- Subject: THIRD PARTY VENDORS -------------------------------------------------------------------------------- 1) Third party vendors for RAM. The following vendors are listed in alphabetical order. No guarantees are made regarding compatibility or relative merit of the vendors. Camintonn Clearpoint Research Corporation 22 Morgan 1000 E. Woodfield Road, Suite 102 Irvine, CA 92718 Schaumburg, IL 60173 (800) 843-8336 (708) 619-9227 (714) 454-6500 Concorde Technologies Dataram 7966 Arjons Dr. B-201 PO Box 7528 San Diego, CA 92126 Princeton, NJ 08543-7528 (800) 359-0282 (800) DATARAM (619) 578-3188 (800) 799-0071 Digitial Micronics Eventide 2075 Corte Del Nogal 1 Alsan Way Unit N Little Ferry, NJ 07643 Carlsbad, CA 92009 (201) 641-1200 Helios Systems Herstal Automation 1996 Lundy Ave 3171 West Twelve Mile Rd. San Jose, CA 95131 Berkley, MI 48072 (408) 432-0292 (313) 548-2001 (800) 366-0283 IEM Infotek Systems P.O. Box 1889 625 South Lincoln Fort Collins, CO 80522 Suite 204 (800) 321-4671 Steamboat Springs, CO 80487 (303) 221-3005 (800) 767-1084 Intelligent Interfaces ISA Ltd P.O. Box 1486 1-1-5 Sekiguchi Stone Mountain, GA 30086-1486 Bunkyo-Ku (800) 842-0888 Tokyo 112 Japan 81-3 (5261) 1160 US Office (Texas) (713) 493-9925 Kelly Computer Systems Kingston Technology Corporation 1101 San Antonio Rd. 17600 Newhope Street Mountain View, CA 94043 Fountain Valley, CA 92708 (415) 960-1010 (714) 435-2600 Martech Merida Systems 1151 W. Valley Blvd. (617) 933-6790 Alhambra, CA 91803-2493 (800) 582-3555 (818) 281-3555 Newport Digital R Squared 14731 Franklin Avenue 11211 E. Arapahoe Rd., Suite 200 Suite A Englewood, CO 80112 Tustin, CA 92680 (303) 799-9292 (714) 730-3644 (800) 777-3478 [ Thanks to Roy McMorran (mcmorran@ll.mit.edu) for the info on RAM suppliers. ] -------------------------------------------------------------------------------- Subject: UTILITIES -------------------------------------------------------------------------------- 1) ASCII to Postscript converter. You can get an ASCII to Postscript converter from ftp.uu.net in the file /usenet/comp.sources.misc/volume10/a2ps3.Z. -------------------------------------------------------------------------------- 2) How do I make perl on HP-UX? Reply like this to Configure: 1. When it asks for optimization flags answer +O1 if you have HP-UX 7.05 or less -O if you have HP-UX 8.0 or later. 2. When it asks for additional flags to cc answer -DJMPCLOBBER 3. When it asks for additional libraries answer -lndbm -lm (ignore the other libraries Configure finds). You can also safely add -lBSD if you wan't BSD signal semantics. 4. When it asks if you wan't to use perl's malloc answer y If you have HP-UX 8.07 or later you may choose to answer no to this since that malloc is OK. 5. When perl asks on which boundarie a double must be aligned answer 8 if you are on a 9000/800 or 9000/700 series machine (HP-PA architecture). 2 otherwise (Motorola 68k architecture) -------------------------------------------------------------------------------- 3) What is the status of the various gnu items on HP-UX? Here's a summary for HP-UX 8.07: All of the results are based on compilation with GCC 2.3.1 and not on the use of the HP C compiler. A section is included in the list for applications that did not compile with GCC but did with HP C. The last part of the listing contains the applications I can't get to compile. If you got them to compile with GCC 2.3.1 and can send me fixes, I'll include them in this list. Note: To compile GCC 2.3.1 with debugging support, you must have the UTAH GAS 1.36 version from jaguar.cs.utah.edu: pa-gas.u3.tar.Z. GNU products that compile fine: ------------------------------ bison-1.19 cpio-2.1 diff-2.0 emacs-18.58 emacs-18.59 (had troubles with installation although it compiles OK) fileutils-3.4 find-3.7 flex-2.3.7 gas-1.36.utah (from jaguar.cs.utah.edu pa-gas.u3.tar.Z) gcc-2.3.1 gdb-4.6 (with pa-gdb-4.6.tar.Z patches from jaguar.cs.utah.edu) ghostscript-2.5.2 (and fonts) gmp-1.2 gptx-0.2 grep-1.6 hello-1.1 indent-1.6 patch-2.0.12u8 perl-4.035 rcs-5.6 sed-1.11 shellutils-1.8 tar-1.11 termcap-1.1 texi2roff-2.0 texinfo-2.16 textutils-1.3 GNU products that don't support (yet?) HP9000/700: ------------------------------------------------- dld-3.2.3 gas-1.38.1 gdb-4.7 glibc-1.05 GNU products that don't compile because another product doesn't: --------------------------------------------------------------- autoconf-1.2 (m4-1.0) groff-1.06 (libg++-2.2) iostream-0.50 (libg++-2.2) nihcl-2.2 (libg++-2.2) GNU products not yet examined (don't have time right now): --------------------------------------------------------- ae finger-1.37 gnuchess-4.0 gnugo-1.1 gnuplot-3.2 ispell-2.0.02 ms-0.06 mtools-2.0.7 smalltalk-1.1.1 tile-forth-2.1 xboard-2.0 GNU products not examined (and I don't plan to): ----------------------------------------------- button.3.00 c-torture-test dirent elvis-1.6 (fine on PC; don't care on HP) f2c-3.2.90 (compilation is more trouble than it's worth) fax-3.2.1 (don't have a FAX modem) fgrep-1.1 (too old to be interesting) malloc-0.1 oleo-0.03.2 (too old to be interesting) readline-1.1 (GDB 4.6 readline lib compiles just fine) uucp-1.03 (UUCP on HP is Honey-Danber) vh-1.3 GNU products that don't compile with GCC 2.3.1 but do with HP C: --------------------------------------------------------------- bash-1.12 bc-1.02 binutils-2.0 m4-1.0 make-3.62 screen-3.2b time-1.4 tput-1.0 [thanks to Pierre Mathieu, mathieu@geod.emr.ca] -------------------------------------------------------------------------------- Subject: X WINDOW SYSTEM, OSF/MOTIF, AND HP-VUE -------------------------------------------------------------------------------- 1) X11R4 Libraries (Athena, etc.) and utilities (imake, etc.). There is a HP maintained, but UNSUPPORTED, set of X11R4 libraries and utilities for the HP 9000 Series 300, 400, 700, and 800. You can get the libraries, include files, and config files (imake) via anonymous FTP from hpcvaaz.cv.hp.com (15.255.72.15) in the directory pub/MitX11R4/libs.s*00.tar.Z. This is also archived on the iworks node as mentioned above. HP has also submitted X11R5 sources to the iworks node as mentioned above. -------------------------------------------------------------------------------- 2) How can I display an image on the root window with HP-VUE? Set Vuewm*backdrop*image: none. Note that there is an explicit pick for this in the Style Manager with HP-VUE 3.0. When the backdrop is clear, you can use xloadimage, xsetroot, xv, or the like to display the image of your choice. -------------------------------------------------------------------------------- 3) How do I get a scroll bar on hpterms? Set the following resources: HPterm*scrollBar: TRUE HPterm*saveLines: 1024 or some other other arbitrarily large number. To do this interactively, use "hpterm -sb -sl 1024". -------------------------------------------------------------------------------- 4) How can I put a title in my hpterm titlebar? Here is a two line program that you might find useful: /* Quick and dirty program to put argv[1] in the title bar of an hpterm Tom Arons March 1992 */ #include <string.h> main(argc,argv) int argc; char **argv; { printf("\033&f0k%dD%s", strlen(argv[1]), argv[1]); printf("\033&f-1k%dD%s", strlen(argv[1]), argv[1]); } [ Thanks to Tom Arons (arons@ash.eecs.ucdavis.edu) for this item. ] -------------------------------------------------------------------------------- 5) How come my hpterms keep going away by themselves? You are probably using the C Shell (/bin/csh) and have autologout set (it is set to 60 minutes by default). Put an "unset autologout" in your ".cshrc". If you are using the korn shell it is probably due to the value set for the shell variable TMOUT. Set it to 0 (infinite timeout). [ Thanks to Jim Sharpe (jms@spatial.com) for the Korn Shell information. ] -------------------------------------------------------------------------------- 6) How come my HP X/Motif clients take a LONG time to display on a Sun? The problem is with the OW3 server. You can request OW3 patch 100444 (or whatever is the current replacement) from Sun to fix the problem. Supposedly this has been rolled into OW 3.0.1. A workaround is to set the X resource *useColorObj: False. -------------------------------------------------------------------------------- Subject: OPERATING SYSTEM -------------------------------------------------------------------------------- 1) Can I have filenames longer than 14 chars? Yes, change to long filenames using /etc/convertfs. You can't go back, though. -------------------------------------------------------------------------------- 2) How can I tell what filesets have been loaded on my system? Check the /etc/filesets directory. There is a file there for each fileset that has been loaded that summarizes the files in that fileset. This directory is used by the /etc/update, /etc/updist, /etc/netdistd, and /etc/rmfn utilities for loading and unloading software. -------------------------------------------------------------------------------- 3) How do I safely remove software from my system? The _only_ safe way to remove HP software is to use /etc/rmfn. -------------------------------------------------------------------------------- 4) What's the scoop on HP-UX 9.0? [ Thanks to Larry Thompson for this information ] |> Here's some information I promised awhile back that I finally got approved |> through channels (probably because most of this is known by now). This |> should not be taken as the final OFFICAL statement on what the differences |> are with 9.0 or all of the differences between the s700 and s800. I think |> this is fairly good list of features. |> |> This was written by the folks who did s700. You will probably notice a slight |> favoritism toward the s700 features. |> |> Anyway I hope someone finds this interesting. (Please don't mail me asking |> for any follow up info. Getting permission to post this was hard enough.) |> |> Oh yeah, |> |> #include <STD_DISLAIMERS> :-) |> |> This is not an offical statement by the Hewlett-Packard Company. It is posted |> with permission from management for the information of our users who read this |> notes group and who's inputs and comments we value greatly. |> |> |> HP-UX 9.0 Differences |> |> |> ------------------------------------------------------------------------------- |> ------------------------------------------------------------------------------- |> |> Major S700/9.0 (IF3) kernel features not in S800/9.0MU |> |> SW disk striping |> Industry standard I/O drivers |> AT&T style configuration |> DUX: There is no diskless capability on 800/9.0MU. DUX is supported on |> S700, S400 and S300 only. A S700 will not boot a S800 and a S800 |> will not boot a S700, S400 or S300. Note: DUX is not MP-safe. |> Graphics support:(bitmap displays, etc.) Graphics is not supported |> on S800/9.0MU. HP 9000 models 835,845 have been obsoleted. Note: |> MP-safe graphics does not yet exist. |> OSF AES Level2 compliant: mmap, iomap,vfork, poll(2) and Berkeley timer |> commands in S700/9.0 but not in S800/9.0MU. |> Memory mapped Files: mmap is only supported in S700/9.0. There are |> several calls in libc for memory mapping. Using mmap in S700/9.0 |> wipes out binary compatibility to S800/9.0MU. Note: MP-safe mmap |> does not yet exist. |> iomap(7): iomap is an OSF1 feature and an administrative difference that |> is supported in the S700/9.0 but is not supported in the S800/9.0MU. |> It doesn't effect binary compatibility. |> vfork: vfork is turned on, it was turned off in 8.0. If used, it will |> provide greater performance on the S700/9.0. However, using |> vfork in the S700/9.0 wipes out binary |> compatibility with the S800/9.0MU. |> poll(2): The use of poll will wipe out binary compatibility between the |> S700/9.0 and the S800/9.0MU. NOTE: poll will be available with the |> S800 Streams product on the 9.0 HTR, Q1 '93. |> Berkeley Timers: New command formats to obtain time-of-day, date, etc. |> Code using the new command format won't work on S800/9.0MU, only on |> the S700/9.0. |> Fast Symlinks: Fast Symlinks are an OSF1 feature providing greater |> performance on the S700/9.0. It is an administrative difference |> that is not supported on the S800/9.0MU. It doesn't effect binary |> compatibility. |> User Virtual Address Space = 1.9GB: The default user virtual address |> space on both the S700/9.0 and S800/9.0MU is 900MB (up from 640MB in |> the 8.x releases). However, there is new linker option, on the |> S700/9.0 only, that expands the user virtual address space to 1.9GB. |> Dynamic Buffer Cache: Dynamic buffer cache is a performance feature and an |> administrative difference that will not effect binary compatibility. |> SCSI immediate report enabled: A S700/9.0 disk performance feature that |> is not supported in the S800/9.0MU. It will effect binary |> compatibility. |> EISA I/O,VME I/O support |> Advise: ISU product only for Apollo Domain |> |> |> Major S800/9.0MU kernel features not in S700/9.0 |> |> LVM |> Powerfail |> MP |> SVID3 features(labelit, sadp, sysdef, volcopy) |> Disk mirroring (datapair) |> Switchover |> SAR |> Hard disk partitions |> BSD style config (uxgen) |> Autoconfig |> mpctl (MP system call) |> Remote access port |> DBsend/DBreceive |> Async disk I/O (Sybase) |> Fairshare scheduler |> AT&T specials (e.g. datakit) |> HP-FL |> NIO, CIO HP-IB |> DTC |> CS-80 Disk support |> ------------------------------------------------------------------------------- |> |> Other 9.0 and 9.0MU differences besides kernel features. |> |> New Math libraries: libm, libM, libcl and libvec all have new versions, PA1.1. |> The old versions, PA1.0, are still supported. PA1.1 gives more |> precise results than PA1.0(a.k.a. "different results in some cases"). |> Plus, the system defaults are different: |> S700/9.0 has PA1.1 as a default with PA1.0 as an option and |> S800/9.0MU has PA1.0 as the default with PA1.1 as the option. |> If reproducing results in applications from release to release is |> more important than performance, then PA1.0 should be used. |> |> cksum(1) utility: The CRC checksum polynomial has changed in both 9.0 and 9.0MU. |> This results in a different number than calculated with older |> versions. Any application using cksum may be impacted. Also the |> cksum output is now - checksum, number of octets and pathname to |> standard output. In previous versions, the number of blocks were |> reported, not the number of octets. Any application using the number |> of blocks that was output along with the checksum will be impacted. |> Blocks = # of Octets/512(Block size). |> |> X11 R5 Server: The X11 R5 server is only supported on the S700 (also S300 |> & S400). The X11 R5 server is not supported on S800 systems. |> |> |> ------------------------------------------------------------------------------- |> |> HP-UX kernel release stream comparisons |> ======================================== |> |> WSBU GSY |> ---- --- |> Design |> center: Technical workload Commercial workload |> tuning tuning |> |> Small # of Large # of |> processes processes |> |> Medium/large processes Small/medium size processes |> |> I/O & interactive OLTP |> performance performance |> |> Low-end size High-end scalability |> Graphical EOU Terminal EOU |> |> Very sensitive to Less sensitive to |> support costs (high volume) support costs (moderate vol) |> |> Technical applications Commercial applications |> & non-OLTP commercial |> |> Peer-to-peer client-server PC-to-mainframe client-server -------------------------------------------------------------------------------- 5) How come HP-UX doesn't support NFS root access? HP-UX versions previous to 9.0 do not support NFS root access to mounted file systems. This because they are at an old revision of NFS. You *can* hack your kernel to provide it, but it's dangerous, unsupported, and a security hole. 9.0 supports full NFS 4.1 functionality, including NFS root. -------------------------------------------------------------------------------- 6) Can I get HP-UX to try DNS ahead of NIS? This is the "standard" answer given from the Response Center: If there is only one IP address in resolv.conf and if the address is the local node's IP add., then NIS or /etc/hosts is used because the IP is reachable and named is not running. if the address is the name server's IP add., if the address is reachable but named is not running, then NIS or /etc/hosts is used (the same reason) if the address is not reachable (eg the node is down) then at 7.0 NIS or /etc/hosts is used; at 8.0 resolution fails. If there are more than one IP address in resolv.conf, no NIS or /etc/hosts fallback will be used after all addresses are tried and failed. In other word, if they only configure one IP address in resolv.conf and are running 7.0, they should be ok. As for additional configuration ... the answer is NO, you can't get it to try NIS before DNS etc ... [ Thanks to Jim O'Shea at the Atlanta RC for this information. ] -------------------------------------------------------------------------------- 7) How come the LOGnnnn files in /usr/adm keep growing and growing? The LOGnnnn files in /usr/adm (8.x except 8.02) or /usr/adm/diag (8.02 and 9.0) are the diagnostic event log files. Kernel drivers send data to the diagnostic system when certain events, usually hw/sw problems, occur. The diagnostic daemons (DIAGMON, DEMLOG, MEMLOGP, DIAGINIT) log the data to these files. There is also a MEMLOG file in the same directories to which MEMLOGP logs memory errors. HP Support uses the logged data to diagnose problems and to predict hardware failure. If the LOGnnnn files are growing (other than creating a new 40 byte file each time the system reboots) then something is wrong with the system. Often what is wrong is that the diagnostics system was improperly installed. Check that the following files exist for each node: /etc/mknod /dev/config c 69 0x000000 /etc/mknod /dev/dmem c 27 0x000000 There are a number of other device files (see /system/CORE-DIAG/customize) but I don't believe they are needed for the logging aspect of diagnostics. If you examine the contents of the log files that may give a clue as to what's wrong. However, the output is intended for HP Support and factory consumption and may not be very intelligible to customers. To examine a log file: $ sysdiag DUI> logtool LOGTOOL> list log=nnnn LOGTOOL> exit DUI> exit where nnnn is the numeric part of the /usr/adm/diag/LOGnnnn file name. The utility logtool is safe to use as far as I know but don't run any other utilities at the DUI prompt--you could easily adversely affect your system. If you have a support contract I recommend you get them to review your log files. There is an extensive help command within sysdiag and logtool. If you want to turn off diagnostic logging just remove execution permission for the file /usr/diag/bin/DIAGINIT. Note that if you do this and your system has a problem later, not having the records logged to diagnostics by the kernel will hamper resolution of the problem. Existing log files can be deleted at the cost of losing the data they contain. The highest numbered log file is the active log file and should not be deleted. There is a sysdiag(1M) man page. As of 9.0 there is a diaginit(1M) man page which documents the various daemons. [ Thanks to Wayne Krone of HP. ] -------------------------------------------------------------------------------- 8) How come I can't lock mail or other files on a Sun? Believe it or not, Sun's lockd is broken at 4.1.x. The proper Sun patch number is Patch-ID# 100075-09, called the "lockd jumbo patch". -------------------------------------------------------------------------------- 9) What are the known issues with HP-UX 8.07? abs() is defined in two places for C++, stdlib.h and math.h. the IDL includes do not support C++ (fixed with patch PHNE_0974). PostScript printing from datebook (week or month) fails. datebook "View Year" display font is goofy looking and doesn't line up. statd can hang when accessing Apollo objects (fixed with PHNE_0690). automounter crashes when -hosts is specified (fixed with PHNE_0936). virtual memory performance problems (fixed with PHKL_1065). -------------------------------------------------------------------------------- 10) Why are mail files in /usr/mail are owned by daemon instead of the recipient? The mail delivery agent /bin/rmail needs to be able to chown(2) these files. It cannot do so if you have removed the privilege CHOWN (see setprivgrp(1m); removing CHOWN is recommended to prevent cheating on disk quotas). To get around this, noting that /bin/rmail runs setgid to group mail, you can grant privilege CHOWN to group mail only by inserting the line "mail CHOWN" in /etc/privgroup. The change takes effect on the next reboot, or immediately if you execute the command "setprivgrp -f /etc/privgroup". [ Thanks to Jim Richardson (jimr@maths.su.oz.au) for this submission. ] -------------------------------------------------------------------------------- 11) How can I tell if I need more than a 2-user license? There are several fundamental things to remember about HP-UX licensing: o Series 700 and Series 800 users are now counted the same way o Display console counts as one user o Each ASCII terminal counts as a user, regardless of how it is connected o The LAN connection counts as one user Ascii Terminals The simple rule to remember is any ASCII terminal that is logged in counts as a user. ASCII terminal connections can come in several different forms: o Direct-connected via a serial terminal multiplexer o Connected via Data Terminal Concentrators (DTCs) or via terminal servers o Personal Computers (PCs) acting in terminal emulation mode, whether connected via serial line or via Local Area Network (LAN) X-terminals and workstations When a customer buys an X-terminal or workstation from HP or from another vendor, HP acknowledges that the customer has also bought a single Unix license-to-use. Therefore, the customer has the right to an unlimited number of logins and terminal windows _over_the_LAN_ to a Series 700 or Series 800 from either X-terminals or workstations. These logins can be via X terminal windows (_hpterm_ and _xterm_), _telnet_, _rlogin_, or other means. PC's that use X-terminal emulation software such as XView each count the same as an X terminal. This is because the PC essentially becomes an X-terminal when it is running the X server software. Therefore, when a PC is running an X-terminal emulator, the PC has the right to an unlimited number of logins to an HP-UX system.